home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
guilib.zip
/
READ.ME
< prev
Wrap
Text File
|
1993-03-01
|
12KB
|
235 lines
G U I L I B
(G)raphical (U)ser (I)nterface (LIB)brarian
Inventory list:
READ.ME Documentation for installation
GUILIB.EXE PM Library change control system
BTRCALLS.DLL Btrieve dynamic link library
GUIBTR.DLL Btrieve access for GUI products
GUISEC.DLL Security module
GUIPRINT.DLL Print module
GLUSERS.BTR User profiles
GLMESSAG.BTR GUILIB Message data
GLASSOC.BTR GUILIB File Associations
GLBRANCH.BTR GUILIB Branch data (code branching)
GLLANG.BTR GUILIB Languages
GLOUT.BTR GUILIB Checked out data
GLPROD.BTR GUILIB Product profiles
GLMAIN.BTR GUILIB Main file database
GLLINK.BTR GUILIB Product link data
GLUPDATE.BTR GUILIB Update history data
Other ABS products;
ABSCOMP.EXE PM File compare utility
EZDOS.EXE File management utility OS/2 and DOS
GUIMAIL.EXE PM Mail system
***************************************************************************
WARNING!!! -- This application (GUILIB) is NOT FREEWARE!!! It is a
Shareware application and MUST be registered after 30 days.
Please register your copy as I value any and all comments about this
system and I need to know if I should continue developing the system. I
appologize for not having any real documentation yet. The documentation
is currently being written.
***************************************************************************
Be warned, this is pre-release code and is subject to lots of changes.
DON'T trust it with your only copy of your source and object files. Keep
regular backups.
GUILIB requires OS/2 1.2 or higher and can run in a stand-alone
environment.
On the NETWORK select a drive designator to assign to the Library
system. This should be a drive assigned to a PUBLIC directory, that is
everyone that enters the network has read/write/create/delete access to.
Create a directory called \LIBRARY or any other name of your
choice. Copy all of the files into this directory.
The user rights for the \LIBRARY area should be read, execute,
and write. The system will create a directory off of the \LIBRARY
directory called USERAREA. Users should have all rights to this as this
is where the user specific work files are placed.
For this example we have chosen drive P:. On the network the
LAN alias for the public area on this system is called LIBRARY. In the
network it is known as \\LAN99\LIBRARY.
*********************************************************************
Change config.sys as follows on each MACHINE:
Add to LIBPATH=...;P:\LIBRARY;
SET PATH=...;P:\LIBRARY;
SET DPATH=...;P:\LIBRARY;
SET GUILIB=P:\LIBRARY
MAKE SURE THAT THERE ARE NO ; or \ or ANYTHING ELSE AFTER THE
PATH.
NOTE: Some people may be pointing to the root of LIBRARY after doing
the net use command. These people should have their GUILIB= as;
SET GUILIB=P:\
*********************************************************************
On each machine add the following to the STARTUP.CMD file.
LOGON XXX9999 /P=YYYY (THIS WILL LOG THE USER ONTO THEIR NETWORK)
(XXX = IDENTIFIER, 9999 = EMPLOYEE ID.)
(YYYY = PASSWORD TO THE NETWORK)
NET USE P: \\LAN99\LIBRARY <- THIS WILL ASSIGN DRIVE P: TO USER
P:
CD \LIBRARY <- CHANGE TO LIBRARY DIRECTORY CREATED BY YOU
START GUILIB.EXE XXX9999 /P=YYYY /I <- START GUILIB, LOGON TO IT)
C: ( /I = ICONIZE SYSTEM)
To get started, start up GUILIB from the desk top. A Logon
panel will appear. Use the User ID of "Master" and a password of "PASSWORD"
(NOTE: logons are CASE sensitive). Select from the action bar, "Edit" and
then "Users...". This will bring up a panel for adding and updating user
information.
Add yourself as a Library Administrator and all others as Normal
Users. When adding user ID's, I would suggest using the same ID as you
use on the Network logon. Set up all default passwords the same and
instruct your users to logon and change the default.
All information except the Net Address and the Middle initial
is mandatory. I would also suggest that you make the users working
directory the same as the user ID or as close as you can make it if you
use ID's longer than 8 characters. ALL WORK DIRECTORIES SHOULD BE
UNIQUE!!!!
To add a new product to the library, select New from the File
pulldown on the action bar. This will display a dialog asking for a new
or existing product name. If you type in a new name, the program will ask
for a drive and directory of where to add this product. I would suggest
that you place it under the same directory as the GUILIB executables.
Using the example above, this would be P:\LIBRARY\PRODNAME. This will keep
each product in its own directory structure. The next thing that will
happen is an Association dialog will "Pop" up.
The Association dialog is where you describe the characteristics of
your product. It asks for the following information;
Group Name: This would be a name for the main type of file
that will be placed in this group, i.e., Executables,
Source, Link, Support, etc.
Sub Group Name: This further breaks down the Group into components;
Exec, Dynamic Link Libs, Help Manager, Cobol, Headers,
etc.
File Pattern: This is the file pattern of all files that will be
placed in this Group - Sub Group; *.EXE, *.DLL, *.C,
*.HLP, *.CBL, etc.
Directory: This is the path spec of where these files will be
placed. I would suggest that all of one group go
in the same directory. This is not a requirement.
Ex.; P:\LIBRARY\PRODNAME\EXEC
File Type: Two choices exist, Source and Non-Source. Source files
MUST be text files. These files will be run thru
the file compare function at check-in time to keep
deltas of all the changes. Non-Source files are
simply copied back into the library at check-in time
and only the log files are updated.
Attributes: Normal file attributes settings.
Language: This is an optional field that can be any source file
language name like Cobol, C, Pascal, etc.
Max Users: This tells the system how to lock the files at check
out time. If it is set to 1, only one user at a time
may check out the file. Set to a higher number, the
system will allow up to that many copied of the file
to be checked out. At check in time, all source changes
from each user are merged back into the original copy.
NOTE: GUILIB makes no assumptions that the merged code
is valid. All source file should be re-compiled and
re-tested.
Template Push Button: Once you have a product setup the way you want
it, you can hit this button for a New Product to pull
in the Associations from an existing product. This
will keep you from having to re-type everything for
each product.
The last step in adding a new product is to add the files. When you
exit the Associations dialog, a File dialog will appear. This dialog allows
you to change the drive and path to where your existing files are placed.
When you see your files in the list box, you may then manually select the
files you want placed in the library, or you may hit the Select All button.
The Select All button runs thru the list and selects all files that match the
Associations file patterns. If a file pattern is not used, the file will
not be selected. When you hit the Ok button to accept the list, all of the
selected files will be copied to the library and put into their proper
directories.
At this point you are now ready to start the check out, check in
process.
As always, everything has a price. The price for using this is
$15.00. This will register you as a user and will allow me to send you
upgrades of the system as they are made.
If you have any problems, give me a call or write at;
Mike B. Baker
Automated Business Solutions
6548 Brookside Cr.
Columbia, S.C. 29206
(803) 782-4777
╔═════════════════════════════════════════════════════════════════════════════╗
║ Registration ║
╠═══════════════════════════════════════╦═════════════════════════════════════╣
║ Name ║ Title ║
║ ║ ║
╠═══════════════════════════════════════╩═════════════════════════════════════╣
║ Company ║
║ ║
╠═════════════════════════════════════════════════════════════════════════════╣
║ Address ║
║ ║
╠════════════════════════════════════╦════════════════════════════╦═══════════╣
║ City ║ State ║ Zip ║
║ ║ ║ ║
╠════════════════════════════════════╩════╦═══════════════════════╩═══════════╣
║ Business Phone ║ Fax # ║
║ ║ ║
╠═════════════════════════════════════════╩═══════════════════════════════════╣
║ Date ║
║ ║
╠═════════════════════════════════════════════════════════════════════════════╣
║ Product(s) ║
║ ║
╠═════════════════════════════════════════════════════════════════════════════╣
║ Comments ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ ║
║ ║
╚═════════════════════════════════════════════════════════════════════════════╝